Workgroup Modeling Reports
Modelers typically work from a common set of libraries and models, and share information about these objects with other users. One way to share information is by using reports, which details the information and definitions for a model. You can generate predefined reports to view the contents of specific libraries and models, view the changes and conflicts for specific models, and view the security structure for the database.
You can generate Mart reports using either the Report Designer, the Query Tool, or a third-party reporting tool.
- Report Designer
-
Report Designer lets you create a wide variety of mart administrative reports and cross-model reports. You can create report templates for frequently used reports and you can export reports to the HTML, CSV, and PDF formats. You can create report solutions and include multiple report templates. For more information about the Report Designer, see the Online Help.
- Reporting Tool
-
You can create custom reports using a third-party reporting tool. For more information about generating custom reports, see the Creating Custom Mart Reports using a Reporting Tool guide.
erwin Data Modeler Workgroup Edition includes the following predefined reports:
- Cross Model Reports
The following table describes the cross-model reports that you can run against Mart:
Report Name |
Description |
---|---|
Attributes/Columns |
Provides information about attributes/columns of the mart models |
Design Layer Lineage |
Provides information about the model sources of the mart models |
Domains |
Provides information about Domains and Datatypes of Attributes of the mart models |
Entities/Tables |
Provides information about the entities/tables of the mart models |
Naming Standard |
Provides a list of mart models that have active naming standard objects |
Relationships |
Provides relationship information, such as parent and child tables of mart models |
Subject Areas |
Provides information about the subject areas of the mart models |
User Defined Properties |
Provides information about the UDPs present in the mart models |
Views |
Provides information about the views present in the mart models |
The following table describes the filters available for the above reports:
Report Name |
Filter By |
Description |
---|---|---|
Attributes/Columns |
Only The Attributes Within Entity |
Filters attributes that are only part of entities |
Only The Attributes Without Comment |
Filters columns without Comments |
|
Only The Attributes Without Definition |
Filters attributes without Definition |
|
Only The Attributes Without Domains |
Filters attributes whose domain is a default domain |
|
Specify Attribute Name at Run Time |
Filters the attribute whose name is specified at run time |
|
Specify Model Name at Run Time |
Filters the model whose name is specified at run time |
|
Design Layer Lineage |
Specify Model Name at Run Time |
Filters the model whose name is specified at run time |
Domains |
Search Domain Name at Run Time |
Filters the domain whose name is specified at run time |
Specify Model Name at Run Time |
Filters the model whose name is specified at run time |
|
Entities/Tables |
Only The Attributes Without Comment |
Filters columns without Comments |
Only The Attributes Without Definition |
Filters attributes without Definition |
|
Specify Attribute Name at Run Time |
Filters the attribute whose name is specified at run time |
|
Specify Model Name at Run Time |
Filters the model whose name is specified at run time |
|
Naming Standard |
NSM_Option-Show Only Active NSM |
Filters NSM Objects that are Active in Mart Models |
Relationships |
Exclude Relationship On View |
|
Specify Model Name at Run Time |
Filters the model whose name is specified at run time |
|
Specify Relationship Name at Run Time |
Filters Relationship Names that are present in the Mart and whose name is specified at run time |
|
Subject Areas |
Search Subject Area Name at Run Time |
Filters the subject area whose name is specified at run time |
Specify Model Name at Run Time |
Filters the model whose name is specified at run time |
|
User Defined Properties |
Search UDP Name at Run Time |
Filters the UDP whose name is specified at run time |
Specify Model Name at Run Time |
Filters the model whose name is specified at run time |
|
Views |
Search View Name at Run Time |
Filters the view whose name is specified at run time |
Specify Model Name at Run Time |
Filters the model whose name is specified at run time |
The filters available are mutually exclusive. Therefore, you can select only one of them at a time.
- Mart Administrative Reports
The following table describes the mart administrative reports that can be run against models in the mart:
Report Name |
Description |
---|---|
Libraries |
Provides information about libraries present in the mart |
Locks |
Provides information about locks present in the mart, such as the models and catalogs that are locked |
Models |
Provides information about the models saved in the mart |
Profiles |
Provides information about the profiles present in the mart |
Sessions |
Provides information about the mart user sessions, such as the session status |
User Logs |
Provides information about the actions performed by mart users |
User Permissions |
Provides information about the permissions present for mart users |
Users |
Provides information about mart users, such as the user type |
The following table describes the filters available for the above reports:
Report Name |
Filter By |
Description |
---|---|---|
Libraries |
No Filter |
|
Locks |
No Filter |
|
Models |
No Filter |
|
Profiles |
No Filter |
|
Sessions |
Active Session |
Filters active user sessions |
Current User |
Filters all information of the user that is logged on currently or the use that runs the report |
|
User Logs |
User-Exclude Deleted Users |
Filters log result of users, excluding the deleted users |
User-Specify Users at Runtime |
Filters the user whose name is specified at run time |
|
Session_Log-Filter By Category- Authentication |
Filters log-in, log-out, and authentication failure logs |
|
Session_Log-Filter By Category- Catalog |
Filters actions performed on the Catalog Manager, such as open and close, initial save, incremental save, create catalog, and delete catalog |
|
Session_Log-Filter By Category- Log |
Filters users that cleared logs using the Log Management pane of the erwin Mart Portal |
|
Session_Log-Filter By Category- Misc |
Filters logs of miscellaneous actions that are not covered under any category. For example, report execution |
|
Session_Log-Filter By Category- Permission |
Filters logs of actions performed using the Permissions pane of erwin Mart Portal |
|
Session_Log-Filter By Category- Profile |
Filters logs of actions performed using the Profile Management pane of the erwin Mart Adminsitrator |
|
Session_Log-Filter By Category- User |
Filters logs of actions performed using the User Management pane of the erwin Mart Portal |
|
Session_Log-Filter By Type- Error |
Filters logs of actions that are registered as errors |
|
Session_Log-Filter By Type- Info |
Filters logs of actions that are registered as information. This is the default level for all actions except for actions that result into errors. |
|
User Permissions |
Exclude Delete Users |
Filters permission information of users, excluding deleted users |
Users |
Exclude Delete Users |
Filters information of users, excluding deleted users |
The filters available are mutually exclusive. Therefore, you can select only one of them at a time.
- Bulk Editor
The Bulk Editor provides the selection, validation, and maintenance of model object metadata, permits reusable customization (option sets), and realtime access to model changes. Export results or selected rows to a CSV file. You can use the Bulk Editor to edit a small set of properties over a large number of objects. Changes and updates are immediately committed as you make them, field by field.
For more information, refer to the Using the Bulk Editor topic.
- Query Tool
The Query Tool is used to query the repository through executing SQL SELECT statements against a local model or a model in the mart. You can use the Query Tool to create your own .QRY report file. Save your option set locally to the model or as an XML file. Export your results to a CSV file. You can execute a query against the objects and properties in the model, the metadata defining those objects and properties, and the action log that records the changes that are made to your model during the modeling session. You can create new queries or paste text from another source (such as a .SQL file) into a query. Although the Query Tool provides a built-in query interface in erwin Data Modeler, you can also use any third-party reporting tool that has ODBC capability to query erwin Data Modeler modeling data.
For more information, refer to the Query Tool topic.
Copyright © 2025 Quest Software, Inc. |